A store should be software you own

Mercury exists because the founders spent a decade building commerce platforms and watched every customer end up renting their own store. This is the engine they wished they could have licensed.

Why we built it

Mercury started in 2023 as the back end of one store. The founders had run commerce engineering at two platforms and watched the same thing happen at both: the store the customer paid for was never really theirs. Every feature was an app, every app owned a slice of the data, and leaving meant starting over.

So they wrote the engine they wished they could have licensed — orders and stock as ledgers, checkout as a single hosted page, and every feature behind one public API — and released it under Apache 2.0. Cloud came a year later, for the teams who wanted the same code without the pager.

Today Mercury runs stores in forty countries, from a ceramics studio that sells out in minutes to a marketplace with sixty producers behind one checkout. The engine is still the engine. Nobody has to leave.

1,200
Stores in production
40
Countries
2,100
GitHub contributors
$1.4B
Processed last year

Three things we will not trade

  1. 01

    Own the code that runs your store

    A store is a business's most important software. It should not be rented. Every line of Mercury is Apache 2.0, and Cloud is the same code with someone else on call.

  2. 02

    Boring where it counts

    Orders, money, and stock are ledgers. We model them as ledgers, append-only and reconcilable, and put the creativity into the storefront instead.

  3. 03

    The API is the product

    The admin, the checkout, and every starter theme are built on the same public API you use. If we cannot do it through the API, neither can you, so we fix the API.

The people on call

Twenty-eight of us across Copenhagen, Lisbon, and Austin. Every engineer ships to the open-source engine; every support answer comes from someone who has.

See open roles
  • Ada Lindqvist

    Ada Lindqvist

    Co-founder, CEO

  • Marcus Oyelaran

    Marcus Oyelaran

    Co-founder, CTO

  • Yuki Sato

    Yuki Sato

    Head of Design

  • Ines Duarte

    Ines Duarte

    Engineering, Checkout

  • Theo Bakker

    Theo Bakker

    Engineering, Platform

  • Amara Diallo

    Amara Diallo

    Developer Relations

Build the store with us

Clone the engine, open a Cloud project, or come work on it. Either way, start tonight.

Start building See open roles